-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Filebeat] Add access_key_id, secret_access_key and session_token into aws module config #17456
Conversation
Pinging @elastic/integrations-platforms (Team:Platforms) |
This is great and offers a lot of flexibility for our users. I'm wondering if we should add an authentication section to the docs to explain what happens when the various auth variables are set and what combo to use them in? The s3 input docs already has the "aws-credentials-config" section. Could we maybe link to that? |
@leehinman Good point! I will add the link. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…t_access_key and session_token into aws module config (elastic#17484) * [Filebeat] Add access_key_id, secret_access_key and session_token into aws module config (elastic#17456) (cherry picked from commit 64aeb2d)
What does this PR do?
This PR is to add missing configuration parameters into filesets under aws module.
Why is it important?
With this PR, users will be able to use
access_key_id
,secret_access_key
andsession_token
directly in Filebeat aws module.This PR also adds the missing config for
ec2
fileset into defaultaws.yml.disabled
config withenabled: false
.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.